fix(ts): use type-only imports in TS variants (fixes TS1484 in stock Vite react-ts apps) - #1018

Follow-up: I understated the impact in the description. For at least one component this is not a tsc complaint at all — it breaks the bundler and the dev server, with TypeScript entirely out of the picture.

Ballpit imports WebGLRendererParameters from three, which is a type. three does not export it at runtime, and unlike the other cases the name survives into the emitted module.

Production build, stock Vite React-TS app, tsc skipped so only the bundler runs:

$ npx vite build
error during build:
Build failed with 1 error:
[MISSING_EXPORT] "WebGLRendererParameters" is not exported by "node_modules/three/build/three.module.js".
 4 │ import { ACESFilmicToneMapping, ..., WebGLRenderer, WebGLRendererParameters } from "three";
   │                                                     ╰───────────── Missing export

Dev server, same app, measured with Playwright:

So Ballpit's two TS variants cannot be built or run at all in a stock Vite app today, regardless of anyone's tsconfig.

Why this one and not Silk: in Silk, IUniform is its own single-specifier import { IUniform } from 'three', and an import statement whose only specifier is unused after type erasure is dropped before it reaches the bundler. Ballpit's sits inside a 21-name import whose other names are genuine values, so the statement survives — and carries the type name with it. That is why the failure looks inconsistent across components rather than universal.

Nothing changes in the diff; the type modifier this PR adds at Ballpit.tsx:25 is what fixes it. Just wanted the severity on the record, since "compile error" undersells a component that currently fails vite build outright.

Pushed 6ad9ba0: the registry artifacts were missing from this PR.

public/r/*.json embeds the component source verbatim and is what the jsrepo CLI writes into a user's project, so fixing only src/ left the shipped payload with the value imports intact. That includes Ballpit's WebGLRendererParameters, which is the one that makes rolldown fail the build outright rather than just upsetting tsc.

Regenerated with npm run registry:build; 83 entries change, all TS variants.

Slimmed this down and rewrote the description with a reproduction.

Two things changed since you last would have seen it:

• The generated public/r/** artifacts are gone — the diff is source only now. That was 83 of the ~166 files and it was pure noise, npm run build regenerates them.
• The description now has a copy-pasteable repro showing tsc failing on main in a stock Vite react-ts project, and passing on this branch.

Worth calling out explicitly: this repo's own tsconfig.json doesn't set verbatimModuleSyntax, so your CI genuinely cannot catch this — the break only shows up in the consumer's project after they copy a component. That's why there's no failing test here to point at.

Happy to split it per-category if a single 83-file diff is awkward to review.